Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Map mozilla positions to web-features IDs #1034

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Map mozilla positions to web-features IDs #1034

wants to merge 2 commits into from

Conversation

captainbrosset
Copy link

@captainbrosset captainbrosset commented May 29, 2024 •
edited
Loading

The web-features repository maintains a growing list of web platform features. This list acts as a hub for various web data such as browser-compat-data, Can I Use, specs, WPT, Chrome's usage counters, etc.

The most useful thing the web-features repo offers right now is a summary of browser support and a Baseline status per feature. The Baseline status, in particular, is used on the MDN Web Docs and Can I Use websites.
Other websites such as webstatus.dev use a bunch of information from web-features.

The W3C WebDX CG (which currently maintains the repo) recently discussed mapping web-features entries to browser standard positions too.

This PR is a proposal for the first step towards achieving this. It adds IDs of features in the web-features repo to individual entries here. This is done by adding an optional webFeaturesID property to entries in activities.json. This property is a string which value matches filenames in https://github.com/web-platform-dx/web-features/tree/main/features (without the file extension).

If you agree with this approach, this will help us link Mozilla positions with a lot of other data about web platform features around various web properties.

I plan on proposing a similar PR for https://webkit.org/standards-positions/

cc @jgraham who we discussed this with.

@captainbrosset captainbrosset mentioned this pull request May 29, 2024
Open
foolip
foolip reviewed May 29, 2024
View reviewed changes
activities.json Outdated Show resolved Hide resolved
@captainbrosset
Copy link
Author

I could use help for an additional mapping:

  • webFeaturesId: registered-custom-properties
  • Possible IDs in this repo: css-properties-and-values-api or at-property.

Any idea which one I should be mapping to?

This was referenced May 30, 2024
Open
Closed
@zcorpan
Copy link
Member

zcorpan commented May 30, 2024

Thanks for this PR!

We're considering moving away from maintaining activities.json for each request, and instead mostly use GitHub labels. Right now some requests with a position aren't listed in activities.json. Maybe we can use labels for web features though.

@captainbrosset
Copy link
Author

We're considering moving away from maintaining activities.json for each request, and instead mostly use GitHub labels. Right now some requests with a position aren't listed in activities.json. Maybe we can use labels for web features though.

This sounds very similar to how WebKit does it then. Using labels would indeed work, but it means that your team would have to maintain these labels (mostly remembering to add the label in the first, web-features IDs are very unlikely to change over time).

@foolip foolip mentioned this pull request Jul 30, 2024
Open
@captainbrosset captainbrosset mentioned this pull request Sep 6, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@foolip foolip foolip left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
tooling
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@captainbrosset @zcorpan @foolip